Conversation
|
@isc-shuliu this PR is related to #550 where part of running "update" should upgrade a module and run its upgrade steps (if any). |
Thanks for the heads-up! I'm aware of that hence posting it as a draft. |
| } | ||
| } | ||
|
|
||
| ClassMethod CanUpdate(modName As %String, semver As %IPM.General.SemanticVersion) As %Boolean |
There was a problem hiding this comment.
@isc-shuliu Doesn't look like this method is used?
There was a problem hiding this comment.
Yes, you're right. I haven't gone to that point yet. My plan is to show if an outdated package can be updated to a particular version without violating dependency constraint. This PR is still a Work-In-Progress
|
Hi @isc-shuliu and @isc-kiyer |
|
@AshokThangavel this work is definitely sitting around unowned at the moment, so feel free to pick it up. Note that this change was started before the |
|
Hi @isc-dchui |
|
Hi @isc-dchui |
|
@AshokThangavel Oh interesting. I'm not too familiar with the differences between them so I'd say go explore and figure out which is appropriate in this situation (and why they're different in the first place). |
|
Thank you! The |
Implement an
outdatedcommand mentioned in #427